Pull Request Test Coverage Report for Build 19209180643

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-85.3%) to 0.0%

Totals
Change from base Build 19209151625:	-85.3%
Covered Lines:	0
Relevant Lines:	0

💛 - Coveralls

Pull Request Test Coverage Report for Build 18467157949

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-85.3%) to 0.0%

Totals
Change from base Build 17751474096:	-85.3%
Covered Lines:	0
Relevant Lines:	0

💛 - Coveralls

Blocked by python 3.13 (#440) / python 3.14 support.

Django 5.1 is still officially supported till EOY and shouldn't be removed.

@mspiller is there any reason not to use 5.2 instead ?

Well 5.1 is still supported and will be till end of the year. Having tooling that does not support officially maintained versioned is a PITA. For example we managed to migrate one of the projects from 5.1 to 5.2 just yesterday.

And before you ask :D Yes development libs are updated more often than runtime env like Django that needs lots of testing before going to prod.

Sure (I put back 5.1), but I was just wondering as it's a minor version upgrading should be uneventful ? (as even upgrading a django major is uneventful in my experience)

It seems something important was broken by modification in pylint 4 (lots of issue with a lot of things.). Do you have an idea what broke @carlio ?

It's finding errors in test files called func_noerror.... which are supposed to generate no errors ; my guess is that the plugin isn't being loaded by the test runner, so things which should have no errors because pylint-django supresses them are instead erroring.

This is just a guess from looking at this locally, I'll keep looking but that insight might help.